-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix handling of gdpr object #3756
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi,
I tested the changes on hello_world and gdpr_hello_world pages. Just one issue here that request to 'https://orbidder.otto.de/bid' gives me an 403 error, can you please check this at your end.
Rest of the things seem to be working fine. Thanks.
The gdprConsent object is now there in the request payload for 'https://orbidder.otto.de/bid', hence approving the changes.
The backend does some checks against the account id, so that's why you got the 403 error. I just double checked, things are running fine now. Do you need anything else for the changes to be merged? |
* initial orbidder version in personal github repo * use adUnits from orbidder_example.html * replace obsolete functions * forgot to commit the test * check if bidderRequest object is available * try to fix weird safari/ie issue * ebayK: add more params * update orbidderBidAdapter.md * use spec.<function> instead of this.<function> for consistency reasons * add bidfloor parameter to params object * fix gdpr object handling
Type of change
Description of change
gdrp data is erroneously retrieved from validBidRequest item instead of bidderRequest. This cannot work and has got to be fixed.